no-issue

All together on: #686

Summary

Adds zod schemas and transforms for every SDK function that takes RPC/client input. Schemas validate JSON input and transforms convert it to SDK-ready arguments -- RPC URLs become viem clients, private keys become accounts, strings become bigints. The target audience here is devs who are already familiar with zod, and helping them to write scripts without messing up the arg parsing, and letting them follow a opinionated structure. Devs who arent familiar with zod dont get benefit here, but it's not a complicated library to learn, and I think it's a useful thing to know about.

WARNING: we're creating schemas for every function, so there's a lot of code being added here, but two things are worth focusing on which help us to gain confidence in the correctness of the code:

• The schema type tests - here we're trying to test that the output of the transformed schema could be directly into its equivalent sdk function, so if you're confident those tests work then in theory the schemas are good from a correctness point of view
• In all cases where we can we set the return type of the schema transform to Parameters

Not included for now

• Additional parsing libs. Now that we have zod schemas which will parse json, we can use existing tooling to convert yaml, env vars or cli args to json and than parse with the same schema giving scripts more options of what they expose to users.
• Describe() - we can add documentation to the schemas to give consumers and idea of what values to put into the params. Those descriptions can be accessed via a dry-run/help command or zod can be converted into json schemas to directly expose the documentation.
• Documentation and readme. Three sets of documentation is required: one for sdk maintainers, one for script writers and one for users of the cli.
• Extending the CLI with some standard useful scripts to be used by SRE/other consumers